Performance-based logistics for aerospace and defense programs

ABSTRACT

This invention relates to an automated method and system for forming and implementing a performance-based logistic contract through managing the maintenance an item of equipment in accordance with a maintenance plan. Embodiments of the present invention include a method and system for maintaining an item of equipment supports the provision of predictive maintenance in a manner which eliminates or reduces downtime of the equipment. The method includes tracking performance data on the equipment or a particular component of the equipment. At least one required maintenance activity is predicted based upon the performance data with respect to a defined performance standard. Performance of the required maintenance activity is scheduled at a defined respective time based upon the prediction.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is continuation-in-part application to 11/490,774, filed on Jul. 21, 2006, which is a divisional of U.S. application Ser. No. 10/799,914, filed Mar. 12, 2004, which is a continuation-in-part of each of the following U.S. application numbers.: U.S. Ser. No. 09/947,157, filed Sep. 4, 2001; and U.S. Ser. No. 09/946,032, filed Sep. 4, 2001; and U.S. Ser. No. 09/946,095, filed Sep. 4, 2001; and U.S. Ser. No. 09/946,894, filed Sep. 4, 2001; and U.S. Ser. No. 09/947,136, filed Sep. 4, 2001; and U.S. Ser. No. 09/947,024, filed Sep. 4, 2001; and U.S. Ser. No. 09/946,160, filed Sep. 4, 2001; and U.S. Ser. No. 09/825,633, filed Apr. 3, 2001; and U.S. Ser. No. 09/690,793, filed Oct. 17, 2000. All of these application are incorporated herein by reference

FIELD OF THE INVENTION

This invention relates to an automated method and system for forming and implementing a performance-based logistic contract through managing the maintenance an item of equipment in accordance with a maintenance plan.

BACKGROUND

Product acquisition and sustainment have traditionally been separate and not necessarily equal concerns. The government's primary focus has been on the acquisition of technology and systems. Additionally, the government has had a number of secondary concerns: sustainment of the system, technology transfer, and the development of an industrial base to support the system long term. The ultimate goal in an acquisition strategy is to build both partnerships and relationships that align the goals of all organizations for the duration of the program. Once the competition for the initial acquisition of a system has occurred, the ability of the government and the contractor to make substantial changes in the system is typically limited. Since some acquisition efforts last for decades, it is essential for the parties to explore the acquisition strategy carefully before embarking on a course of action. This is especially so as, over the life cycle of most systems, it has been estimated that about 30 percent of all dollars spent are used to acquire the system, while the remaining 70 percent of all dollars are used for support.

The goal of both acquisition and sustainment is to gain the most efficient and effective performance of the system for its entire life. In doing so, it is important to realize that acquisition and sustainment are not separate but simultaneous and integrative issues that require analysis and synthesis throughout the product life cycle. Ultimately, the challenge for the program manager is to structure optimal relationships with contractors through the use of appropriate contractual mechanisms, agreements, and incentives.

The 2006 Quadrennial Defense Review from the Department of Defense (DoD) highlights the need for a more agile approach to global sustainment. This need for agility will also extend to the DoD's contractors. Accordingly, there is a needed to provide rapid and flexible readiness and sustainment support on a global basis. Moreover, contractors need to be proactive, rather than reactive, working as a partner with the DoD to help determine needs. Likewise, contractors should advocate appropriate new products and technologies, rather than wait for Requests for Proposals (RFPs) and specifications from the DoD. This requires contractors to assume financial risk, and then rigorously manage programs to minimize that risk and drive profitability. Moreover, these process need will accelerate up-front development and improve upon products already in the field, as well as allow contractors to operate with a culture that can adapt quickly to changes in customer requirements and missions.

Changes in DoD strategy have increased the importance of sustaining the readiness of the existing equipment installed base. The DoD and its Aerospace and Defense (A&D) suppliers currently have a limited number of new platforms under development. Thus, focus has shifted to supporting and maintaining the existing equipment base, with a significant amount deployed on active duty. In addition to support, the focus in the defense industry is on managing the existing installed base of equipment

Performance based logistics (PBL) is an acquisition approach used by the Department of Defense (DoD) and represents an integrated Performance-Based Environment (PBE) for both acquisition and sustainment. This is very appropriate since dollars spent on maintenance continue to increase as systems age. (See, e.g., Performance Based Logistics: A Program Manager's Product Support Guide, available at https://acc.dau.mil/GetAttachment.aspx?id=32536&pname=file&aid=6154), the subject matter of which is hereby incorporated by reference in full.

Under the traditional paradigm of purchasing equipment, the DoD would purchase equipment and then, as needed, would purchase parts or repairs as needed. Under PBL, the DoD contracts for a performance outcome, i.e., a certain level of availability of the equipment, without specifying how that performance outcome is to be accomplished. PBL is not a single strategy, but rather a framework for developing a tailored strategy on a case-by-case basis. Common to all PBL arrangements is the goal of contracting based on performance rather than on specific parts or services delivered.

Thus, a PBL contract must specify metrics by which performance can be measured. High-level PBL metrics are operational availability, operational reliability, cost per unit usage, logistics footprint, and logistics response time. Operational availability is specified as a percentage of time that a system is available. Operational reliability is specified as a percentage of mission success objectives met. Because the specific mission objectives vary depending on the type of system, a measurement objective might be a tour, launch, sortie, or other system-specific objective. Cost per unit usage is the total operating cost divided by the appropriate unit of measurement for a given system. For example, the unit might be miles driven, flight hours flown, hours of service, or some other system-specific unit. Logistics footprint is a measure of the size of the support personnel, equipment and facilities required to maintain the system. Logistics response time is a measure of how long it takes to deliver parts, systems, and labor to support the system. For any given acquisition, these PBL metrics will be specified in a way that makes sense for the specific acquisition, and performance requirements will be built into the acquisition contract. In order to bid on a such a contract, a contractor must be able to determine the likely cost of meeting the DoD's desired performance.

For example, the Navy Aviation Tires PBL program includes a performance metric. The program supplies more than 20 different sizes of tires for over a dozen different types of military aircraft. The contract requires 95% on-time delivery of tires, where on-time delivery is defined as two days within the United States and four days outside the United States. It is up to the tire suppliers to manage their supply chains in order to meet that contractual goal.

However, the DoD has determined that existing PBL contracts are not being executed well. For example, new contracts should take advantage of repeatable processes, systems and other assets. Moreover, the DoD is looking to outsource support of existing equipment and, more specifically, to implement PBL contracts with its A&D suppliers and to collaborate more closely with its partners. This presents a significant opportunity to A&D contractors that can effectively deliver profitable and repeatable PBL contracts.

As a result, there is a need for government contractors to be able to predict with reasonable accuracy the likely support costs of a piece of equipment in order bid effectively. Further, because contractors are held to performance measures rather than simply being able to bill for parts and labor used, there is a need for contractors to be able to predict with reasonable accuracy the likely needs for parts, labor, and other equipment, in order to minimize costs resulting from either inadequate or excessive inventories, unnecessary shipping costs, and ineffectively utilized personnel.

Toward these and other goals, there is a current need for an improved system and method to allow PBL providers to demonstrate a core set of capabilities. Specifically, PBL providers should provide global depot and field maintenance activities, including transportation and logistics. PBL providers should also assess PBL value through business case development. At the same time, PBL providers need to manage technical support services, including technical documentation while supporting configuration management, such as “as-built” and “as-maintained” management. The PBL providers preferably develop, measure, and report upon PBL program metrics. Thus, the PBL providers should actively monitor and measure system/platform performance while ensuring DoD-mandated levels of system/platform uptime. To carry out these functions, the PBL contractors should create, manage, and support a human resource pool to carry out PBL activities, as well as acquire, track, and maintain government property in support of the contract.

A primary cause for problems in PBL contracts is poor management of inventory, maintenance, and repair. In the prior art, maintenance of an item of the equipment may occur only after discovery of a defect or deficiency found during an inspection of the equipment. The inspection of the equipment may be performed incidentally to other maintenance activities or the inspection may be part of a scheduled program of maintenance. The scheduled program of maintenance may be organized based upon data or recommendations provided by a manufacturer of the equipment.

Prospective maintenance activities may include maintenance, repair, and overhaul activities. Prospective maintenance activities are planned and identified based on one or more prior inspections of equipment. If the inspections are delayed or too infrequent to uncover an actual or future deficiency, a user of the equipment may experience reduced availability of the equipment. For example, an actual or future deficiency may prevent use of the equipment or may result in a failure of the equipment during routine operation. Further, if the maintenance schedule provided by the manufacturer does not accurately reflect the true performance or reliability of the equipment, a user of the equipment may experience unwanted downtime. If the equipment, when properly functioning, is capable of generating revenue, the downtime of the equipment may negatively impact financial results of a business associated with the equipment. Similarly, if the equipment is essential for manufacturing or other uses, the downtime of the equipment may negatively impact financial results of a business associated with the equipment. Accordingly, a need exists for a method or system for maintaining an item of equipment according to a maintenance plan where unwanted downtime of equipment is reduced or eliminated.

A configuration defines the identity of the components (e.g., parts), a specification of the components, and the relationship among the arrangement of components of an item of equipment, among other things. Because some components are interchangeable with substitutes, the configuration of the item of equipment may vary throughout a life span of the equipment as maintenance activities (e.g., maintenance, repair, and overhaul) are performed. The configuration of the item of equipment may change because of a revision of product definitions or a review (e.g., a financial and performance review) of the item of equipment. Further, even during the manufacturing process, the manufacturer of the equipment may substitute different components (e.g., parts) from different suppliers to customize the equipment, to meet a certain technical specifications for the equipment, or to save manufacturing costs on the equipment. For example, the manufacturer may change technical specifications of equipment to rectify manufacturing anomalies or to facilitate more reliable production. Thus, standard as-built documentation on the equipment may contain erroneous information on the configuration of the equipment.

Maintenance, overhaul and repair personnel may keep few records of the actual configuration of the equipment because of over-reliance on the manufacturer's specifications, manuals, and as-built documentation. Even if configuration records are available, the records may be difficult to use or access. Thus, a need exists for promoting the maintenance of accurate records on equipment-related work with ready access to maintenance, overhaul and repair personnel.

SUMMARY OF THE INVENTION

This invention relates to an automated method and system for forming and implementing a performance-based logistic contract through managing the maintenance an item of equipment in accordance with a maintenance plan. In accordance with the invention, a method and system for managing the maintenance of an item of equipment supports the provision of maintenance in a manner which eliminates or reduces downtime of the equipment. Configuration maintenance requirements are determined for maintaining a target configuration of an item of equipment. Predictive maintenance requirements are determined for the item of equipment based on at least one of a longevity estimate, a probability of failure, and a financial analysis. A data processing system plans for the availability of at least one of resources and a component for performing maintenance consistent with the configuration maintenance requirements and the predictive maintenance requirements.

Strategic Sourcing, life cycle asset management, planning and logistics integration, and the service performance technology and management may be adapted to a PBL contracting scheme. For example, embodiments of the present invention disclosed herein provide for predicting maintenance requirements and amplifies the utilization of configuration information to include functional, logical, physical, and operational configurations and environments as a part of the prediction process. In these embodiments, predicting maintenance requirements is broadly enough structured to include all of the existing prediction tools and methods, whether used singly or in combination.

Likewise, embodiments of the present invention disclosed herein include performing predictive maintenance on equipment, and using these techniques to maximize the PBL performance. For example, a PBL framework may include a data processing system that stores a first database of component data on components of equipment, a second database of maintenance personnel associated with corresponding qualifications, and associates at least one predictive maintenance factor (for a component) with the corresponding component data. A scheduler then schedules maintenance for a maintenance time period for at least one of the components based on the first database, the second database, the associated predictive maintenance factor, and an elapsed time with respect to an installation date of at least one component. The predictive maintenance factor may be defined by one or more of the following: a longevity estimate, a probability of failure, a financial estimate on maintenance of a component, a known down time period of the equipment, a known linkage of a predicted maintenance task to other maintenance tasks, or similar conditions.

Embodiments of the present invention disclosed herein may further include achieving predictive maintainability in maintenance, repair, or overhaul (MRO) which focuses on robust prediction of what work needs to be accomplished (and when) based on actual conditions and the prediction of task need. This is the 180-degree movement away from current “check the checklist item based on approximated service life, and see what you can find” practices, and relies on robust configuration management, prediction via proven analytical tools, application of Activity Based Management and Costing principles, leaving the opportunity open of using the component and system descriptions and their contexts to establish configurations (contextual semantics analysis), and wrapping it all together by utilizing a solid MRO Business Model to determine functionalities and infrastructure approaches.

Embodiments of the present invention disclosed herein may further include an MRO Business Process Model and establishes the various analysis tools which are built off of the model (Operational Assessment tool; Functionality to Software selection method; etc).

Still further embodiments of the PBL framework include identification, categorization, and integration of unplanned work. These methods of rigorously and consistently describing “over and above” work, including the linkage of planned work to the “newly found” tasks, and establishes the concept of using the geography within an end item as to where tasks are located to assist in gathering those tasks together. Included within the patent is the forward planning for “probable but unplanned” MRO tasks, and their linkage to planned work. Included within the this embodiment of the PBL framework are the ideas surrounding standard categories of unplanned MRO work task, standard kits, and the packaging of required information at the task level.

Embodiments of the present invention disclosed herein include performing planning, scheduling and allocation of MRO Resources, a unique approaches required for MRO in the planning of a resource usage (of whatever type), the usage of configuration data as a primary driver of the resources, integration of Activity Based Cost models, the integration of manpower skill and certification requirements, and the optimization of these numerous resources via definable toolsets and custom algorithms. Primary focus in this implemention is the time window available for MRO task performance, and how the numerous resources must be aligned in support of the time available.

Another embodiments of the present invention includes performing Component Provisioning or Issue in an MRO Environment. In this embodiment, the utilization of configuration data (of whatever type) establishes the baseline components requirement for MRO tasks, links to the supply chain providers for what/when/by whom provided for the components, views the end item maintenance schedules and plans, and modifies the acquisition plans per the predictive maintenance models. For example, the PBL contacting framework helps to establish the categories of kits within the realms of virtual, soft allocated, hard allocated, and disbursed. In fact, embodiments of the PBL contacting framework may be included within the patent is the application of potential component requirements as well as the integration of “above and beyond” (unplanned) requirements.

Still another embodiment of the PBL contacting framework includes Multi-Dimensional Configuration Management. The embodiments of the PBL contacting framework cover robust configuration management within an MRO context, and introduces the concepts and definitions for managing configurations beyond the traditional physical configuration to include functional, logical, and operational configurations. Further augmenting the patent are the included subjects of redundant component configurations (multiples of the same component in “hot start” mode) as well as potentially “self healing” configurations (multiple functionality duplicated on chips, or logically enabled to “work around” functionally disabled physical configurations).

In another embodiment, the PBL contacting framework may include a software to configuring mechanical equipment. In accordance with the invention, a method and system of managing a configuration of mechanical equipment provides a structured procedure for managing information on parameters of the mechanical equipment to facilitate the maintenance of safety, legal compliance, performance, and reliability of the mechanical equipment. A desired configuration of the mechanical equipment is defined based on a design objective, such as safety, reliability, performance, or any combination of the foregoing objectives. An actual configuration of the mechanical equipment is determined based on an evaluation of the physical condition of the mechanical equipment. Upgrade requirements are planned for upgrading the actual configuration to the desired configuration if the actual configuration is noncompliant with the desired configuration. The system and method for managing a configuration of mechanical equipment facilitates the consistent attainment and sustenance of a desired configuration of the mechanical equipment in a timely manner. The desired configuration may involve compliance with a regulatory standard, meeting a technical specification, and improving reliability of the mechanical equipment through proper selection and interaction of the parts or assemblies of the mechanical equipment.

Another embodiment of the PBL contacting framework includes Planning and Scheduling Modifications to Multi-Dimensional Configurations. In this way, the present invention covers integration of all of the various forms of equipment configuration status data, and the maintenance execution status, and establishes the method of setting cut in points (and dates) for updating configurations.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a block diagram of a system for managing maintenance in accordance with the invention.

FIG. 2 is a block diagram of the system for managing maintenance that shows an illustrative embodiment of the data sources of FIG. 1.

FIG. 3 is a block diagram of the system for managing maintenance that shows an illustrative embodiment of the management systems of FIG. 1.

FIG. 4 is a block diagram of the system for managing maintenance that shows an example of the contents of the storage device of FIG. 1.

FIG. 5 is a block diagram of the system for managing maintenance that shows one embodiment of the logical and/or physical data paths between various elements of the system.

FIG. 6 is flow chart of a method for managing the maintenance in accordance with the invention.

FIG. 7 is flow chart of a method for managing the maintenance with respect to configuration maintenance in accordance with the invention.

FIG. 8 is flow chart of a method for managing the maintenance with respect to predictive maintenance in accordance with the invention.

FIG. 9 is a block diagram of a system for managing maintenance in the environment of a communications system.

FIG. 10 is a block diagram of another embodiment of a system for managing maintenance that communicates to workers via wireless infrastructure.

FIG. 11 is a block diagram of an embodiment of a system for forming and implementing a Performance-Based Logistics contract.

FIGS. 12-19 are block diagrams of components used in embodiments of the PBL system of FIG. 11.

FIG. 20 is flow chart of a method for creating and implementing a PBL contract in accordance with the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In response to these and other needs, embodiments of the present invention provide a performance-based logistics (PBL) framework 600 for aerospace and defense programs (A&D) as depicted in FIG. 11. As depicted in FIG. 11, the PBL framework 600 generally includes a management model 601 to assist an organization to prepare for a PBL contract, a key business capability model 602 to best implement the PBL contact, and an Information Technology support module 603 to support the implementation of the PBL contract. The operation of these modules, along with their sub-modules within the PBL framework 600 is discussed in greater detail below.

Referring back to FIG. 11, the management module 601 generally includes business and development (BD) planning and strategy module 610, complex program integration module 620, and an Organizational alignment and change management module 630.

The BD planning and strategy module 610 operates to defining the roadmap for forming and implementing a PBL contract. In particular, the BD planning and strategy module 610 addresses the value proposition by quantifying the potential risks and value of a global integrated asset management solution and by defining the activities necessary to mitigate those risks, obtain identified value, and meet customer expectations. The BD planning and strategy module 610 prompts potential service providers to define aspects of the PBL contract, including potential internal risks and risks to the customer inherent in PBL; customers wants in a PBL solution and value to be provide; the ability to successfully scale PBL capabilities up and down in response to demand; alignment of sales and field forces to sell and provide services and solutions for the PBL instead of A&D products; transforming an organization from a cost center to one focused on P&Ls; and differentiating from competitors.

With this information, an organization can better prepare and implement a PBL contract by defining program risks and preparing to mitigate these risks, perhaps by reflecting strategy against reality with rigorous pragmatism. Moreover, as described above, a PBL contract entails creation of a metric and monitoring organizations performance on that metrics. Thus, the information collected by the BD planning and strategy module 610 may be used to establish program metrics that measure against any strategy and evaluate the metrics efficacy. The organization can then ensure that strategy and other plans are effectively communicated within the organization and with channel partners as necessary and prepare to flex scale program up or down as needed to comply with contract requirements and DoD needs. For example, a BD planning and strategy tool 611 illustrated in FIG. 12 may be used to guide an organization in the planning structure changes as needed for the PBL contract.

Continuing with FIG. 11, the complex program integration module 620 includes a set of tools to allow an organization better success with a global integrated asset management solution (as necessary for strong PBL performance) by addressing a service provider's ability to manage and integrate a diverse and disparate set of supplier, client, and internal systems and processes. Optimally, the complex program integration module 620 prompts potential service providers to determine the infrastructure and processes required to manage a mix of outsourcing providers and trading partners. Furthermore, the complex program integration module 620 includes several templates to guide an organization to determine which internal skills are needed to manage a complex, global workplan. Furthermore, the complex program integration module 620 may assist users to define the key financial metrics for grading the success of the solution and how should they be measured. For example, the complex program integration module 620 may supply exemplary metrics or otherwise obtain a RFP to define the metrics. Furthermore, the complex program integration module 620 can assist a user to define a place to design activities to be spread across the solution ecosystem without diluting design quality. Likewise, the complex program integration module 620 can evaluate the collected to data to better determine haw a global integrated asset management capability can be used to provide advantages in dealing with offsets.

Consequently, the complex program integration module 620 assists the user to establish a program management office that engages all key stakeholders, which creates a standard rhythm of communication between disparate trading partners. Furthermore, the collected data may be used to help ensure that clear service level agreements are established across all supply chain partners—suppliers, customers, etc. while creating a set of well-understood program metrics to measure compliance to and the success of program initiatives. For example, in one embodiment, the complex program integration module 620 may include a complex program integration tool 621, as depicted in FIG. 13 to guide an organization in the planning of a product and related service in compliance with a PBL contract.

For the reasons described, the success of a global integrated asset management solution often depends upon the service provider's ability to manage and integrate a diverse and disparate set of supplier, client, and internal systems and processes. Problems that arise in performing this task include determining the infrastructure and processes required to manage a mix of outsourcing providers and trading partners and internal skills are needed to manage a complex, global workplan. Again, key financial metrics may be needed for grading the success of the solution and how should the metrics be measured. Therefore, the organization should design activities to be spread across the solution ecosystem without diluting design quality. These and other aspects allow a global integrated asset management capability be used to provide advantages in dealing with offsets.

To address these and other needs, the organizational alignment and change management module 630 helps a user to identify business goals and to develop organizational models to support them. This allows an organization to manage organizational alignment and change management activities centrally as well as within individual programs. To improve overall success, the organizational alignment and change management module 630 helps to identify and contact key offices to involve the responsible executives throughout the organizational change process. Furthermore, the organizational alignment and change management module 630 includes functionality to monitor and measure the organization's ability to retain changes and avoid returning to previous structure. Therefore, an organizational alignment and change management tool 631, as depicted in FIG. 14, may guide users in creating a process for adapting an organization for PBL contracting, along with defining steps in the process and a timeline for the process.

Continuing with FIG. 11, the key business capability model 602 optimally includes a Strategic Sourcing module 640 to drive the realization of benefits on successive waves of spending categories. Issues addressed by the Strategic Sourcing module 640 include determining how cross-functional teams are formed for each category, and determine what is being spent (i.e., a projects volumes, specs, prices, suppliers). More specifically, the Strategic Sourcing module 640 collects information on the structure of the relevant supply market. As for the contract, the Strategic Sourcing module 640 prompts a user to define the drivers of value creation, the criteria for final selection, and the procurement strategy to be adopted. With this data, the Strategic Sourcing module 640 may assist a user to determine what suppliers to retain in the contracting process for Requests for Information (RFI) requests for proposal (RFP) and requests for quotes (RFQ) process. Likewise, using the contract information, the Strategic Sourcing module 640 can help the user to determine the best negotiation strategy, as well as identify a need for various tools, such as eSourcing tools. If the PBL contact is then awarded, the Strategic Sourcing module 640 helps a user to determine a strategy to be used to implement the new negotiated contracts.

In embodiments of the present invention, the Strategic Sourcing module 640 focus on Total Cost of Ownership for various inventoried parts and goods. The Strategic Sourcing module 640 helps to prioritize and execute commodities in waves, as well as coordinating programs, that tend to be not line projects. The Strategic Sourcing module 640 further creates commodity teams from cross-functional resources. The Strategic Sourcing module 640 baselines and validates execution rigorously, as well as optionally managing behavioral and cultural change. A Strategic Sourcing tool 641, as depicted in FIG. 15 enables users to collect supply chain information and to form a supply plan as needed to best meet the goals of satisfying the PBL criteria while minimizing costs.

Returning again to FIG. 11, the key business capability model 602 may further include a life cycle management module 650. In the context of PBL, the life cycle asset management module 650 assists the user to design products for availability and maintainability while simultaneously implementing the organizational structure to support a service-focused organization. Aspects of the life cycle asset management module 650 include identifying capabilities to manage and monitor product configurations—e.g., project as-built and/or as-maintained. Through the life cycle asset management module 650, a user may determine the new requirements that will be placed upon the warranty management organization through the PBL contract and how these requirements should be managed. For example, the life cycle asset management module 650 prompts a user to identify DoD Product lifecycle management (PLM) requirements. PLM is the process of managing the entire lifecycle of a product from its conception, through design and manufacture, to service and disposal. The DoD may require, for example, the contractor to assign Item Unique Identification (IUID) or Radio-frequency identifications (RFIDs) to various components. IUID is a system of establishing globally ubiquitous unique identifiers within the DoD. RFID is an automatic identification method, relying on storing and remotely retrieving data using devices called RFID tags or transponders.

The life cycle asset management module 650 leverages known to tools to allow users to effectively share technical documentation internally and with trading partners. Likewise, the life cycle asset management module 650 may include tools to address whether strategies and capabilities in place to manage technology insertion and upgrades. For example, the life cycle asset management module 650 may include a tool to determine the Return on Investment (ROI) from Research and Development activities whether the ROI can be increased.

It should be noted that as part of a PBL solution, the life cycle asset management module 650 promotes a culture in which the organization can understand that any design covers the entire product lifecycle, and does not end with the handoff from engineering to manufacturing. This incorporation of serviceability and maintainability into product design will drive PBL. To further the PBL ideals, the life cycle asset management module 650 can guide a user to involve all parts of the organization, from product development through maintenance and repair in the life cycle asset management process. For example, as depicted in FIG. 16, a life cycle asset management tool 651 included within the life cycle asset management module 650 may allow a user to effectively plan the product life cycle while ensuring that various key components with the organizational are included in the life cycle plan.

Because PBL requires the contractor to provide cradle-to-grave service, comprehensive planning and logistics are used to match service demand with the supply of both physical and human capital. To address these and other needs, the key business capability model 602 may further include a planning and logistics integration module 660 to perform the various planning and logistics integration functions, such as identifying and planning to satisfy both spares and original equipment demand. The planning and logistics integration module 660, as described in greater detail below, further allows a user to adapt an existing field force to have the ability to meet increased demands upon job scheduling, mobile inventory planning, and dispatch. For example, the planning and logistics integration module 660 may drive OEP planning systems to be integrated across suppliers and customers. Furthermore, embodiments of the present invention, as disclosed below, the planning and logistics integration module 660 may perform profitability analyses on repair, replace, and overhaul decisions. Other aspects of the planning and logistics integration module 660 may include identifying whether transportation and warehouse planning capabilities in place for internal and third-party facilities and whether these facilities are integrated.

In performing these and other functions, the planning and logistics integration module 660 optimally focuses on interoperability in planning across the entire value chain, while prompting users to extend planning capabilities to services as needed for PBL contracting and performance. For example, the planning and logistics integration module 660 may be used to establish well-understood planning metrics that feed into customer Service Level Agreements (SLAs). Optimally, the planning and logistics integration module 660 include tools for organizational change management. Organizational change management includes processes and tools for managing the people side of the change at an organizational level. These tools include a structured approach that can be used to effectively transition groups or organizations through change. When combined with an understanding of individual change management, these tools provide a framework for managing the people side of change. For example, a planning and logistics integration tool 661 depicted in FIG. 17 may include various functions to drive a user to schedule changes and actions throughout product life cycle.

As can be appreciated, PBL brings with it an increase in the number of trading partners, the volume of information transacted between them, and the complexity of that information. Successful execution of PBL will largely depend upon the ability to quickly dissect, interpret, and act upon data. To address these needs, a service performance technology and management module 670 assists a user to collect enough data from across a supply chain to adequately monitor performance, as needed for PBL measurements. The service performance technology and management module 670 may further analyzes supply chain and organizational data to better identify and to predict future problems. The service performance technology and management module 670 may be adapted to include a feedback loop from real-world data back into product design. In this way, the service performance technology and management module 670 may be used to establish a performance management framework that extends across the supply chain and to measure the financial performance of the program over time.

The service performance technology and management module 670 assists the user to centrally manage information and to identify the correct data to collect from across the supply chain. With this data, a user can react to better ensure that lessons learned will be circulated across the supply chain and to create a data-focused organizational mindset. For example, a user may seek to better understand the potential effects of proposed changes to better understand the risk and rewards of various actions, while anticipating the needs of customers and focusing on financial performance. Thus, a service performance technology and management process 671 allows a user to better achieve these tasks through a circular process in which collected data is used to predict events, changes are planned and implemented in response to the predicted events, and additional data from the changes is collected.

Continuing with FIG. 11, the Information Technology support module 603 may include an IT and business tools module 680. PBL is a significant IT integration challenge. In order to optimize the PBL supply chain, contractors, suppliers, and customers systems need to be integrated at a reasonable cost to exchange the data that fuel the supply chain. The IT and business tools module 680 allow the organization to exchange data not only with channel partners but also within the enterprise. The IT and business tools module 680 should allow the organization's IT infrastructure to scale both up and down in a cost effective manner and to provide business intelligence tools needed to support PBL analytics across the enterprise, For example, the IT and business tools module 680 may look to IT investments by trading partners and customers and comparing these estimates to those of the organizations. The IT and business tools module 680 may further analyze customers' IT requirements and determine whether the organization meets these requirements as needed to remain contract compliant. For example, the IT and business tools module 680 may allow a user to develop metrics to measure the business value of IT services. In this way, the IT and business tools module 680 may help a user to develop flexible and scalable IT architectures and to view business intelligence as a key piece of processes and decision making by approaching integration with a focus on utilizing open web standards to the largest degree possible. Furthermore, theses aspects of the IT and business tools module 680 engage suppliers and customers in technology architecture discussions and focus on the ROI of IT. For example, the IT and business tools module 680 may include an IT evaluation tool 681 depicted in FIG. 19 that assists user to gauge various IT areas to identify areas of strength and areas in need of improvement.

Turning now FIG. 20, embodiments of the present invention further include a PBL contracting method 700. The PBL contracting method 700 generally includes acquiring contract information, generally from the DoD RFP in step 710. From this data, the contractor can determine product requirements in step 720 and determine service requirements in step 730, and use these requirements to define PBL performance criteria, step 740.

With, the Product, Service, and PBL criteria defined, the contractor can than set out to plan and implement the Product and Service requirements in steps 750 and 760. Various known product life-cycle exists to plan and implement the DoD product requirements. While the steps of planning and implementing the product requirements in step 750 and service requirements in step 760 are presented as separate, distinct aspects, it should be appreciated that there is significant interplay between the two step. For example, in planning a product specification, the selection of a high quality component may increase initial production cost, but minimize subsequent service duties and expenses through decreased maintenance needs. Various tools and techniques for planning and implementing the product requirements in step 750 and service requirements in step 760 are disclosed herein in FIGS. 1-10, and described in greater detail below.

Following the planning and implementing the product requirements in step 750 and service requirements in step 760, the PBL criteria may be evaluated in step 770, and this data may be used to adjust in step 780 the planned implementation the product requirements in step 750 and service requirements in step 760, as needed to improve PBL performance or to adjust to changes in environment or contractual need. Furthermore, the adjust in step 780 of the planned implementation the product requirements and service requirements allows a contractor to adapt for new contractual needs. For example, a product initially designed for a particular environment (e.g., a wet tropical climate) may need to be adjusted for use in another area (e.g., artic or desert), therefore requiring different components and service.

As used herein, a maintenance provider shall include any person or business entity that performs or supports maintenance, repair, or overhaul activity (i.e., an MRO activity) for at least one item of equipment. Similarly, as used herein, maintenance, a maintenance activity or a maintenance task shall include at least one of maintenance, repair, and overhaul (i.e., MRO) of an item of equipment or a component of the equipment, unless otherwise noted.

A component means a component of an item of equipment, a sub-component of an item of equipment, an assembly of an item of equipment, a system of an item of equipment, or any other constituent part of an item of equipment. A component may be defined based on its relationship with other components in an item of equipment and based upon the context of its use in the equipment. A component may include, but need not include, one or more sub-components. An assembly may comprise a group of integrated or inter-related components. A material refers to a raw material, a consumable material, a component, a provision, or another equipment-related resource concerning the performance of a maintenance activity.

In accordance with the invention, FIG. 1 shows a maintenance system 11 for managing maintenance of at least one item of equipment. The maintenance system 11 comprises one or more data sources 10 (e.g., external data sources) that communicate with a data processing system 12. The data processing system 12 cooperates with a storage device 29. The data processing system 12 communicates with one or more management systems 28. A user interface 26 is coupled to the data processing system 12 to allow a user to control and/or monitor the operation of the data processing system 12.

One or more data sources 10 provide input information to a data processing system 12. In one embodiment, the data processing system 12 processes the input information to determine output information for supporting maintenance and commercial activities incidental thereto. The data processing system 12 communicates the output information to one or more management systems 28. Each management system 28 facilitates implementation of maintenance consistent with the output information or other commercial activities in furtherance of maintenance.

In general, the data sources 10 may include one or more of the following: a supplier data source, an operational data sources, a human resources system, a project/personnel management system, a purchasing system/inventory control system, a financial system, a maintenance management system, a maintenance execution system, a maintenance input/output device, an engineering input/output device, a supervisory input/output device, and any additional input/output device that permits the input of data into the data processing system 12.

The data processing system 12 comprises one or more of the following data processing components: a resource planner 14, a universal nomenclature manager 16, a general maintenance controller 18, a predictive maintenance controller 20, a configuration monitor 22, and a communications interface 24. A data processing component may include hardware, software instructions, or both. The resource planner 14 refers to a data processing component for planning the availability of the at least one of the following items for a time interval at a geographic location to facilitate maintenance, repair or overhaul activity: (1) one or more workers, (2) a facility, (3) infrastructure, (4) test equipment, (5) a tool, (6) one or more components, and (7) a resource. The universal nomenclature manager 16 refers to a data management system that manages the translation and/or standardization of data that is used by the data processing system 12 to support maintenance of an item of equipment. The general maintenance controller 18 manages a general maintenance requirement that is not fully addressed by a predictive maintenance requirement and a configuration maintenance requirement. The predictive maintenance controller 20 determines a predictive maintenance requirement, if any, for maintaining an item of equipment. The configuration monitor 22 determines a configuration maintenance requirement, if any, for maintaining an item of equipment. A communications interface 24 supports communications between the data processing system 12 and one or more of the following: a data source 10, a group of data sources 10, a storage device 29, a group of storage devices 29, a management system 28, and a group of management systems 28.

One or more storage devices 29 support storage and retrieval of data for the operation of the data processing system 12. The data processing system 12 may input or output the following types of data: configuration definition data, planned maintenance data, maintenance resources data, general maintenance data, and historical maintenance data. In one embodiment, the storage device 29 may allocate storage dynamically or on a dedicated basis by the type of data to be stored. For example, the storage device 29 may allocate the data among one or more of the following storage allocations: a configuration data storage allocation 30, a planned maintenance data storage allocation 32, a resource data allocation 34, a general maintenance data storage allocation 36, and a historical maintenance data storage allocation 38.

In an alternate embodiment, the configuration data storage allocation 30 comprises a configuration database; the planned maintenance data storage allocation 32 comprises a planned maintenance database; the resource data storage allocation 34 comprises a maintenance resource database; the general maintenance data storage allocation 36 comprises a general maintenance database; and the historical maintenance data storage allocation 38 comprises a historical maintenance database.

The data processing system 12 facilitates integration of maintenance activities including one or more of the following: configuration maintenance, predictive maintenance, general maintenance, unplanned maintenance resource planning, and data management. Configuration maintenance refers to keeping a configuration up to date with engineering changes, technical enhancements, or modifications that are rolled out because of safety, regulatory, performance, or other concerns. Predictive maintenance refers to predicting the potential failure or potential break-down or of a component of an item of equipment and performing maintenance on the item of equipment based on the prediction to reduce or eliminate the down-time and maximize the availability of equipment for use (e.g., commercial use). General maintenance refers to maintenance that is neither predictive maintenance nor configuration maintenance. General maintenance includes at least unplanned maintenance. Unplanned maintenance refers to performing unscheduled maintenance that may be incident to planned maintenance activities or inspections. Unplanned maintenance also refers to performing maintenance to recover from a break-down or an unexpected equipment failure or problem. Resource planning refers to allocating resources (e.g., human resources and components) for a defined time frame and defined geographic location to handle current or prospective maintenance activities. Data management refers to data storage and retrieval, data processing, and communications for support of maintenance activities and other related commercial activities.

FIG. 2 shows an illustrative example of the data sources 10 and of the data processing system 12 that may be used to practice the maintenance system 11 of FIG. 1. Like reference numbers in FIG. 1 and FIG. 2 indicate like elements.

As illustrated in the example of FIG. 2, the data sources 10 include a supplier data source 44, an operational data source 46 (e.g., an engineering source or a maintenance source), a human resources system 48, a financial system 50, any additional input/output 52, and a monitor 40. The monitor 40 may manually or automatically monitor the operational performance or longevity (e.g., time and/or operational cycle compliance) of a part, an assembly, or the equipment. For example, the monitor 40 may provide a report of assembly longevity data or part longevity data for storage in the planned maintenance data storage allocation 32. In one embodiment, the monitor 40 includes an equipment electrical assembly that monitors the performance, conducts a test, or indicates the status of an item of equipment, a component thereof, or an assembly thereof. In one configuration, the electrical assembly includes a sensor 42 that may obtain data or stored data from the item of equipment and may be integrated into the item of equipment along with the equipment electrical assembly 40.

In one embodiment, the additional input/output 52 may include, but is not limited to, a maintenance input/output device an engineering input/output device, a supervisory input/output device or another data input/output device.

As shown in FIG. 2, the predictive maintenance controller 20 comprises a predictive maintenance module 61, a timer 58, and a scheduler 60. The predictive maintenance module 61 and the timer 58 input data to the scheduler 60. The timer 58 provides present time or an elapsed duration measured with reference to the installation date of a component in a particular item of equipment.

The predictive maintenance module 61 comprises at least one of a longevity estimator 62, a probability of failure predictor 64, and a financial analyzer 66. The predictive maintenance module 61 provides a predictive maintenance requirement based on at least one of a longevity estimate, a probability of failure, and a financial analysis. The longevity 62 estimator provides a longevity estimate for an item of equipment or a component thereof based upon input data (e.g., supplier data). The probability of failure predictor 64 provides a prediction or estimate of the probability of failure a component or an item of equipment based upon input data. The financial analyzer provides an economic analysis of a potential maintenance activity to determine an appropriate maintenance plan based on input data. The predictive maintenance module 61 may obtain the input data from a number of sources including, but not limited to, one or more data sources 10, from the user interface 26 or from both data sources 10 and the user interface 26.

In one embodiment, the longevity estimator 62 provides longevity reference data (e.g., a longevity estimate) on a component or an item of equipment to the scheduler 60. Similarly, the probability of failure predictor 64 may provide probability of failure data (e.g., an estimated date of failure or breakdown) on a component or an item of equipment to the scheduler 60.

The financial analyzer 66 accesses a maintenance plan of the data processing system 12. For example, the financial analyzer accesses the planned maintenance data in the storage device 29 and may provide a cost estimate for a potential maintenance requirement based at least on one or more of the following: internal cost data on labor, consumable materials, components, assemblies, indirect costs and direct costs. Direct costs are costs or expenses that are directly associated with maintenance or repair, including parts and labor for a component. Indirect costs are costs or expenses that represent fixed capital costs, sunk capital costs, or other costs that are required to support the business entity performing the maintenance and repair. For example, indirect costs include costs for lease of a repair facility, purchasing of a repair facility, or capital improvement expenses for repair facilities. In an alternate embodiment, the supplier of labor, a supplier of consumable material and a supplier of components may provide external cost data on the planned maintenance activity. Accordingly, the financial analyzer 66 may allow the owner or operator of the equipment to veto the planned maintenance activity that is too expensive to be practical given the internal cost data, the external cost data, or both.

In one embodiment, the scheduler 60 outputs scheduling data or a maintenance plan to the resources planner 14. In turn, the resource planner 14 may output the maintenance plan, with or without modification, from the resource planner 14 via communication interface 24 for transmission to the management system 28. The resource planner 14 determines whether or not the proposed maintenance plan proposed by the schedule 60 will be adopted or modified to provide a coordinated or integrated maintenance plan. The communication interface 24 may support transmission of the maintenance plan or maintenance data consistent with the maintenance plan via the communications network (e.g., the Internet) to the management system 28.

The resource planner 14 coordinates the bringing together of required component data, worker data, tools, instructions, and other information for planned maintenance at a common geographic location where the item of equipment is or will be situated. In the illustrative embodiment of the data processing system 12 of FIG. 2, the resource planner 14 comprises an allocation intermediary 54, a resource availability module 55, and a coordinator 56. The coordinator 56 determines the priority of and integration of maintenance activities based on a predictive maintenance requirement, a configuration maintenance requirement, and a general maintenance requirement for an item of equipment. In one embodiment, the coordinator 56 comprises a reconciliation module for controlling, reconciling, and coordinating predictive maintenance requirements, configuration maintenance requirements, and general maintenance requirements. If the item of equipment is mobile, an additional data storage allocation (e.g., database) storing the location schedule of the mobile mechanical equipment is preferred to carry out the aforementioned coordination.

A resource availability module 55 contains temporal data on when corresponding resources are available for performing a prospective predictive maintenance activity. In one embodiment, the resource availability module 55 contains temporal data and related geographic data on performing prospective predictive maintenance activity. A resource availability module 55 manages one or more of the following types of data: worker data, facility data, tool data and component data. The resource availability module 55 provides prospective availability dates, prospective time intervals, or both for one or more of the following: a worker, a facility, a tool, a maintenance task (e.g., a MRO task), a component, a material, and an item of equipment. In one embodiment, the resource availability module 55 tracks worker data that includes worker identifiers, corresponding qualifications of the workers, and respective geographic locations of the workers. The allocation intermediary 54 supports the interaction of the resource planner with the scheduler of the predictive maintenance controller.

Because the provision of labor and components are coordinated, workers can work to predetermined schedules, planners can facilitate procurement of components (e.g., replacement parts) by referencing reliable forecasts of required components, additional mechanical equipment, or supplies. The data processing system 12 may foster improved availability of a component for maintenance; improved availability of functional equipment, and timely fulfillment of hiring needs of the maintainer or user of the equipment. The terms of contracts with suppliers may be more firm or certain based on the improved availability and accuracy of forecasts and other information associated with the planned maintenance data outputted by the data processing system 12. Accordingly, the predictive maintenance system of the invention is well-suited for fostering improvements in logistics in the procurement of components (e.g., parts or spare parts) and the assignment of maintenance workers at a planned maintenance time.

The universal nomenclature manager 16 manages data to identify components and materials regardless of a manufacturer, supplier, brand, or other source of identity. The universal nomenclature manager 16 facilitates the use of multiple suppliers or manufacturers for a single component to foster availability of components in the event of problems specific to a single manufacturer or region. Further, the universal nomenclature manager 16 facilitates the identification and management of interchangeable components.

In general, one or more management systems 28 may comprise any of the following: a purchasing system, an inventory control system, a personnel management system, an enterprise resource planning system of a supplier, an enterprise resource planning system of the operator of an item of equipment, a maintenance management system, a materials management system, and a maintenance execution system. As shown in FIG. 3, the communications interface 24 facilitates communication with one or more of the following management systems 28: a project/personnel management system 68, a purchasing system/inventory control system 70, a maintenance management system 72, and a maintenance execution system 74.

Referring again to FIG. 2, the communications interface 24 and the allocation intermediary 54 of the resource planner 14 may support electronic commerce or business-to-business transactions among the operator of the equipment and various trading partners (e.g., supplier of components or repair services.) For example, the communications interface 24, the allocation intermediary 54 or both, may support a data format that is suitable for transmission of the maintenance plan to one or more management systems 28 over a communications network 102 (e.g., the Internet, as shown in FIGS. 9 and 10) via the communications interface 24. The communications interface 24 may comprise buffer memory coupled to a transceiver. The communications interface 24 may support a parallel port, a database interconnection, a serial port, or another computer port configuration.

The scheduler 60 or the resource planner 14, or both, determine a maintenance plan or schedule based on resource availability data provided as worker data, facility data, tool data and component data. The maintenance plan is a framework or scheme for performing maintenance (e.g., predictive maintenance) on the equipment. The communication interface 24 provides an interface for allowing the scheduler 60, the resource planner 14, or both to communicate the resultant maintenance plan (or data derived therefrom) over a communication network to a management system 28.

In one example, management system 28 may comprise a supplier data processing system, an enterprise resource planning system, or supplier fulfillment center, for example. The supplier data processing system may support the maintenance entity's ordering of components, materials (e.g., consumable materials), tools (e.g., test equipment or diagnostic equipment) and other resources necessary to complete predictive maintenance of the equipment.

FIG. 4 illustrates an illustrative set of data storage allocations of a storage device 29. The data storage allocations comprise one or more of the following: a configuration data storage allocation 30, a planned maintenance data storage allocation 32, resource data storage allocation 34, a general maintenance data storage allocation 36, and a historical maintenance data storage allocation 38. In FIG. 4, the storage device 29 refers to any computer storage mechanism that supports a magnetic storage medium, an optical storage medium, an electronic storage medium, or any other suitable storage medium.

The configuration data storage allocation 30 stores configuration data which may include any of the following: component data 76, equipment data 78, installation data 80, and desired configuration data 82. In one embodiment, the configuration data storage allocation 30 comprises an actual configuration database, a desired configuration database, an upgrade requirements database, and a supervisory/historical database. The data processing system 12 supports data storage, retrieval, and queries of the databases stored in the storage device 29.

The planned maintenance data storage allocation 32 stores data related to planned maintenance or predictive maintenance, for example. The resource data storage allocation 34 stores resource data which may include any of the following: worker data 84, resource requirements data 86, and resource availability profiles data 88.

The general maintenance data storage allocation 36 stores general maintenance data which may include planned work probable findings data 90, standard repair data 92, standard repair parts list data 94, maintenance repair and overhaul (MRO) geography definition data 96, and planned work geography locator data 98.

The historical maintenance data allocation 38 stores historical data which may include any of the following: historical configuration data 93, historical resource data 95, and historical planned maintenance data 97.

With respect to the configuration data storage allocation 30, component data 76 refers to availability dates and time intervals of a component, a sub-component, an assembly, or a system for installation or maintenance activities. The component data 76 may define availability dates or time intervals of the equipment based upon one or more of the following types of information: a supplier lead times, an anticipated shipment date, an anticipated delivery date or receipt of equipment, an outstanding order, an inventory of a component, sub-component, assembly or system, an expected receipt of a component, sub-component, assembly, system, or like information.

The material data refers to data on the availability of a raw material, a consumable, a component, a provision, or another equipment-related resource concerning the performance of a maintenance activity. For example, the material data comprises: (1) a material identifier that uniquely identifies a particular material associated with a maintenance activity, (2) a geographic location indicator that indicates the location of the material identifier, and (3) a date or time interval to which the geographic location indicator corresponds.

The equipment data 78 defines the availability of a particular item of equipment. For example, the equipment data comprises: (1) an equipment identifier that uniquely identifies a particular item of equipment, (2) a geographic location indicator that indicates the location of the equipment, and (3) a date or time interval to which the geographic location indicator corresponds. The installation date 80 may be associated with corresponding components to determine a length of service of the corresponding component for determination of a predictive maintenance requirement.

The desired configuration data 82 may pertain to on one or more items of equipment. The desired configuration data 82 may define a target configuration of an item of equipment or a component for determination of a configuration maintenance requirement. The desired configuration data contains an equipment identifier (e.g., tail number of an airplane) that identifies the entire item of equipment, a part identifier that identifies a part of the item of equipment, an assembly identifier that identifies an assembly of parts of the equipment, a specification description that describes the specification of a part, and a relationship description that describes the relationship of a part to the equipment or a subassembly thereof. For example, the relationship description may include the mounting position of a part on the equipment. In one embodiment, the desired configuration data may include operating restrictions on the equipment because of the presence of a particular part or a particular arrangement of parts of the equipment.

In one embodiment, the configuration data in the configuration data storage allocation 30 comprises actual configuration that pertains to one or more items of equipment. The actual configuration data contains actual configuration data on the item of equipment that reflects an actual or present status of the equipment. The actual configuration data includes an equipment identifier (e.g., tail number of an airplane) that identifies the entire equipment, a part identifier that identifies a part of the mechanical equipment, an assembly identifier that identifies an assembly or group of parts of the equipment, a specification description that describes the specification of the part, and a relationship description that describes the relationship of a part to the equipment or a subassembly thereof. For example, the relationship description may include the mounting position of a part on the equipment. In one embodiment, the actual configuration data may include operating restrictions on the equipment because of the presence of a particular part or arrangement of particular parts on the equipment.

The actual configuration data, the desired configuration data, and the upgrade requirements data applicable to an item of equipment may vary with time. Accordingly, configuration data on a particular item of equipment may only remain valid for a limited duration. Upon or before expiration of the duration, the configuration is preferably updated. If the contents of the data storage allocations (e.g., databases) are updated with sufficient frequency to avoid outdated configuration data, the update procedure may be referred to as a real-time procedure. The real-time procedure seeks to minimize inaccuracy of the configuration data by reflecting changes to the actual configuration of the item of equipment as the changes occur with a minimal lag time thereafter. Changes to the actual item of equipment may be necessary or proper to facilitate improvement of the actual configuration. Thus, the data processing system 12 and the storage device 29 can support the coordination of maintenance activities (e.g., maintenance, overhaul or repair) in real time on an ongoing basis with the latest actual configuration data and the latest upgrade requirements.

To support real-time determination of a maintenance plan or data derived therefrom, maintenance worker, such as a technician or a mechanic who is responsible for maintaining or repairing the item of equipment, enters actual configuration data into the configuration data storage allocation during or after an inspection or servicing of the item of equipment. The inspection may involve a visual inspection, a physical inspection, a mechanical test, an electrical test, disassembly of portions of the item of equipment, or other activities that might uncover defects or nonconformities with respect to the desired configuration. The data processing system 12 updates the actual configuration data in the configuration data storage allocation as soon as possible after the inspection or the servicing of the mechanical equipment to maintain the accuracy of the actual configuration data.

With respect to the planned maintenance data storage, the data processor 12 compares the actual configuration to the desired configuration. The difference between the actual configuration and the desired configuration may be referred to as the upgrade requirement. The upgrade requirement, a maintenance plan, or data derived therefrom, may be stored in the planned maintenance data storage 32. The difference may comprise one or more of the following: components, materials, and resources. The upgrade requirement defines the departure of the actual configuration from the desired configuration and indicates the necessary actions to bring the equipment into conformity with the desired configuration. The data processor 12 determines the upgrade requirement. The data processor 12 may express the upgrade requirement in terms of (1) a component requirement (e.g., part, assembly or subassembly requirement) and (2) a human resource requirement that is required to bring the actual configuration in conformity with the desired configuration. The upgrade requirements may contain part identifiers of old parts that require updating of a particular mechanical equipment to gain compliance with the desired configuration. The component requirement is not limited to electrical or mechanical hardware. For example, the component requirement may include modifications of software features and software instructions that are associated with or integral to the functioning of the mechanical equipment. The human resource requirement may include the scheduling of one or more maintenance workers (e.g., technicians and mechanics) to install, repair, adjust, reconfigure, replace or otherwise perform a service associated with the component requirement for the mechanical equipment.

With respect to the resource data storage allocation 34, worker data 84 may comprise worker qualifications data, worker geographic location associated with corresponding workers, certifications of workers, experience of workers, worker schedules, and worker availability. The resource requirements data 86 and resource availability profiles data 88 may comprise facility data and tool data, for example. Facility data provides the availability of space for repairing, maintaining, or overhauling equipment. Further, facility data refers to infrastructure at respective facilities for performing certain types of maintenance, repair and overhaul activities on the equipment. Tool data refers to availability dates and time intervals of certain tools to complete corresponding maintenance, repair or overhaul of the equipment. A tool may refer to any device that assists a worker in performing or conducting a maintenance activity on equipment. For example, a tool may comprise a hand tool, a power tool, test equipment, diagnostic equipment, a test fixture, or the like. The general maintenance data storage allocation 36 contains general maintenance data that may be integrated with predictive maintenance requirements, configuration maintenance requirements, or both to form a comprehensive maintenance plan.

The historical configuration data storage allocation 38 retains the historical records of prior configuration alterations. The historical configuration data storage tracks historic configurations of the item of equipment and any associated failure or defect with historic configurations. A description of the failure or defect, a date of detection of the failure of defect, determined causal factors from failure analysis activities, and resolution or repair of the failure or defect are preferably noted in historical maintenance data storage allocation 38. The foregoing failure or defect data may supplement or be used to update mean-time-before failure (MTBF) data provided by the manufacturer on parts or assemblies of the equipment. In turn, the updated MTBF may be used to change the desired configuration with input from engineering over the engineering input/output device 12.

FIG. 5 is a block diagram of a maintenance system that shows an illustrative group of the logical and/or physical data paths 13 between different elements of the data processing system 12 and the storage device 29. Although FIG. 5 illustrates certain logical and/or physical data paths 13, the elements of the maintenance system may interact or communicate with one another in any manner otherwise supported by this disclosure.

In the exemplary embodiment of FIG. 5, the universal nomenclature manager 16, the general maintenance controller 18, the predictive maintenance controller 20, the configuration monitor 22, and the communications interface 24 communicate with the resource planner 14.

The resource planner 14 may communicate with the resource data storage allocation 34 and the historical maintenance data storage allocation 38. The universal nomenclature manager 16 may communicate with the configuration data storage allocation 30. The general maintenance controller 18 may communicate with the general maintenance data storage allocation 36 and the historical maintenance data storage allocation. The predictive maintenance controller 20 may communicate with the planned maintenance data storage allocation 38. The configuration monitor 22 may communicate with the configuration data storage allocation 30 and historical maintenance data storage allocation 38.

Predictive Maintenance

Any of the embodiments of the maintenance system shown in FIG. 1 through FIG. 5 may perform predictive maintenance in the following manner. As sown in FIG. 2, the communications interface 24 may collect performance data from one or more of the following: a supplier data source 44, an operational data source 46 and a human resources data source 48. In one embodiment, the communications interface 24 may collect performance data from an item of equipment where the item of equipment has a sensor 42 or a monitor 40 for feeding performance data to the communications interface 24. The communications interface 24 may analyze, format, or process the performance data into a format which is suitable for interpretation by the predictive maintenance module 61.

The predictive maintenance module 61 predicts a maintenance activity and an associated time interval for the maintenance activity based upon the performance data with respect to a defined performance standard. The combination of an identified maintenance activity and a corresponding time frame, or date for performance of the maintenance activity, represents one example of a maintenance plan.

A user may enter the performance standard data into the performance standard storage via a user interface 26 associated with the data processing system 12. The user interface 26 may accept entry into via a graphical user interface, a keyboard, a pointing device, a magnetic medium, an optical medium, or otherwise. The predictive maintenance module 61 manages the storage and retrieval of at least one performance standard in the planned maintenance data storage 32 or the configuration data storage 30.

As seen in FIGS. 2, 4 and 5, the predictive maintenance module 61 may access component data 76 in the configuration data storage 30 or elsewhere. The component data 76 may comprise a component identifier and other affiliated information, such as whether particular component identifier complies with the performance standard. Further, the configuration data storage 30 may contain any of the following information: a preferable future date for performing predictive maintenance; a time-frame for performing predictive maintenance; a preliminary schedule for scheduling predictive maintenance; an assembly identifier for the identifying an assembly associated with a component, and item identifier for identifying an item of equipment associated with the component, and any other applicable data on a component or an end item of equipment. Information on tentative time frames for performing predictive maintenance may be refined by the scheduler 60, the resource planner 14, or both. Information on relationships between revisable components and related sub-components, a related assembly, or a related system may be used to define the requisite scope of the revision of the maintenance plan.

The predictive maintenance controller 20 may manage the storage of reference performance data on a component of an assembly, a system, an assembly, or the equipment consistent with at least one performance standard. The predictive maintenance controller 20 accepts the collected or observed performance data on the component, an assembly, or equipment and performs a comparison against a reference performance data standard based upon a component, an assembly, or the equipment. If the collected or observed performance data deviates by a material amount or significant amount from a reference performance data of the performance standard, then any affected component, assembly, system or sub-component is identified as suspect. A suspect item requires attention or predictive maintenance to be scheduled. For example, if the collected performance data is noncompliant with the reference performance data of the performance standard, based upon the equipment as a whole, the affected components or assembly of the equipment may be flagged as suspect components. In one embodiment, a user may clear a suspect status by entering an acknowledgement via the user interface 26.

Where the reference performance data refers to the equipment, as a whole, the performance standard relates to the equipment as whole. The identification of components to be replaced or maintained in that equipment may be based upon historical relationships between the particular deficiencies in the collected performance data and likely or probable suspected components.

The predictive maintenance controller 20 determines a preliminary maintenance schedule for performing predictive maintenance. The preliminary maintenance schedule comprises a preliminary proposed date or a preliminary proposed time interval for performing a maintenance activity (e.g., maintenance, repair or overhaul, which may be referred to as MRO) on a suspect sub-component, suspect component, suspect assembly, suspect system, or suspect item of equipment.

In one embodiment, referring to FIG. 2, the scheduler 60 accepts input from both the predictive maintenance module 61 and the resource availability module 55. The scheduler 60 may accept the input of suspect component data and a preliminary maintenance schedule derived from the comparison of the predictive maintenance module 61 of collected performance data to reference performance data. The scheduler 60 accepts the input of the preliminary proposed date or preliminary proposed time interval for predictive maintenance and determines a resultant date or a resultant time interval for performing predictive maintenance based upon a consideration of the resource availability data as related to the suspect data. The scheduler 60 preferably reconciles the preliminary maintenance schedule with temporal resource availability of one or more of the following: workers, facility, tools, components, materials (e.g., a consumable material or a raw material), and equipment.

The scheduler 60 may revise the preliminary maintenance schedule (e.g., the preliminary proposed maintenance date or time interval) to a resultant maintenance schedule (e.g., a resultant maintenance date or time interval) if at least one of the resources is not available consistent with the preliminary maintenance schedule. However, the scheduler 60 may consider substitution of alternate components prior to revision of the preliminary maintenance schedule. Accordingly, the resultant maintenance schedule may be the same as the preliminary maintenance schedule, if all of the resources are available per the preliminary maintenance plan or if an alternate component can be substituted to preserve a preliminary maintenance schedule. The resultant maintenance schedule assures availability of all necessary resources to perform a maintenance activity on the resultant date or at the resultant time interval.

The resource planner 14 coordinates the maintenance schedule of the predictive maintenance requirement with one or more of the following: any general maintenance requirement and any configuration maintenance requirement for the same item of equipment or a similar item of equipment. For example a similar items of equipment may share the same component that requires replacement or may require servicing at a particular facility. The maintenance plan or data derived therefrom may be communicated to a management system 28 in accordance with several alternate techniques. Under a first technique, subject to the approval of the resource planner 14, the scheduler 60 may communicate the maintenance plan via the communications interface or via the resource planner and the communications interface 24. Under a second technique, the resource planner communicates a maintenance plan or data derived therefrom to a management system 28 via a user interface 26.

To schedule predictive maintenance, the predictive maintenance controller 20 may contact the resource planner 14 to determine whether components, materials, workers, and other resources required for the upgrade are, will be, or can be available at a scheduled maintenance time and scheduled maintenance location. The predictive maintenance controller 20, the resource planner 14, or both maintain the availability and reliability of the equipment, to meet a financial objective, to comply with safety requirements, or for other reasons. The resource planner 14 plans for the availability of one or more workers, facilities, infrastructure, components, or other resources for a time interval at a common geographic location to facilitate maintenance, repair or overhaul activity.

Configuration Maintenance

In any of the embodiments of the maintenance system shown in FIG. 1 through FIG. 5, configuration maintenance may be performed in the following manner.

At regular or scheduled intervals, the configuration monitor 22 monitors the existing configuration of an item of equipment to determine whether the item of equipment deviates from a target configuration. The target configuration may be stored in the configuration data storage allocation 30, for example. If the existing configuration differs from the target configuration, the configuration monitor 22 determines that configuration maintenance is needed for the subject item of equipment. Accordingly, once the configuration monitor 22 determines that configuration maintenance is needed for a particular item, the configuration monitor 22 determines the configuration maintenance requirement. The configuration maintenance requirement may be forwarded to the resource planner 14 for coordination of maintenance activities. The coordination may include integration of the configuration maintenance requirement or another maintenance requirement.

To schedule configuration maintenance, the configuration monitor 22 may contact the resource planner 14 to determine whether components, materials, workers, and other resources required for the upgrade to the target configuration are, will be, or can be available at a scheduled maintenance time and scheduled maintenance location. The existing configuration is updated to the target configuration to maintain the availability and reliability of the equipment, to meet a financial objective, to comply with safety requirements, or for other reasons.

General Maintenance

Any of the embodiments of the maintenance system shown in FIG. 1 through FIG. 5 may provide general maintenance for an item of equipment in the following manner.

The general maintenance controller 18 supports maintenance (i.e., one or more general maintenance requirements) that does not fall under predictive maintenance and configuration management. For example, the general maintenance supports maintenance requirements for one or more of the following reasons: (1) unexpected failure or impairment of an item of equipment or a component thereof, (2) a defect discovered incidental to an inspection of an item of equipment or a component thereof, (3) a defect discovered incidental to a test of an item of equipment or a component thereof, (4) damage to a component or impairment of the item of equipment for any reason, including accidental damage, and (5) any unplanned maintenance requirement.

The general maintenance controller 18 supports catch-all maintenance activities as a fallback mechanism where the predictive maintenance requirements and the configuration maintenance requirements may not have initially allocated the necessary resources necessary to perform the desired maintenance (e.g., make a repair). Nevertheless, the general maintenance controller 18 coordinates with the resource planner 14 in a manner that may dynamically reallocate planned resources from secondary items of equipment to meet an unexpected maintenance contingency for a primary item of equipment. Further, the general maintenance controller may reserve a pool of resources for unexpected maintenance activities based upon historical patterns of maintenance activity for particular items of equipment or otherwise. The historical patterns of maintenance activity may be stored as historical maintenance data 97 in the historical maintenance data storage 38, as shown in FIG. 4.

Integrated Maintenance

The resource planner 14 receives one or more of the following: configuration maintenance requirements from the configuration monitor 22, predictive maintenance requirements from the predictive maintenance controller 20, general maintenance controller 18, procurement data on component availability, human resources data on human resources availability, operational data on maintenance resource availability, input data, and any other data associated with maintenance.

The resource planner 14 coordinates and harmonizes one or more of the following: configuration maintenance requirements, predictive maintenance requirements, and general maintenance requirements. In one example, predictive maintenance and configuration maintenance activities may be combined into a single maintenance session, rather than bringing in an item of equipment in for repeated maintenance. For instance, the predictive maintenance controller determines what predictive maintenance is scheduled for the particular item and whether the existing configuration can be updated to the target configuration during the scheduled maintenance, or at some other time.

Independent from the coordination of predictive maintenance and configuration management, the resource planner 14 may integrate or accumulate the requirements for components for one or more items of equipment to place aggregate orders for required components with one or more suppliers via management systems 28. Accordingly, the resource planner 14 may support centralizing of the acquisition of components and materials to drive the acquisition of larger volumes of components and lower costs than would otherwise be possible.

FIG. 6 shows a method for managing the maintenance of an item of equipment in accordance with the invention. The method of FIG. 6 begins with step S50.

In step S50, the data processing system 12 or the configuration monitor 22 determines a configuration maintenance requirement for maintaining a target configuration of an item of equipment. In one embodiment, the configuration maintenance requirement may be determined in accordance with the following procedure. First, the data processing system 12 supports establishing the target configuration of the item of equipment based on a design objective of the item of equipment. The design objective may be based on at least one of a safety concern, a regulatory concern, reliability, and performance. Second, the configuration monitor 22 evaluates an actual configuration of the item of equipment. Third, the data processing system 12 determines if the actual configuration complies with the target configuration. Fourth, if the actual configuration is noncompliant, the configuration monitor 22 or the data processing system 12 establishes the configuration maintenance requirement to maintain the target configuration is defined.

In step S50, the target configuration may be updated based on engineering change, to facilitate compliance with a regulatory requirement, or for another reason. For example, an engineering change may be entered via a data source 10 or via the user interface 26.

In step S52, the data processing system 12 or the predictive maintenance controller 20 determines a predictive maintenance requirement. The predictive maintenance requirement for the item may be determined based on one or more of the following: a longevity estimate, a probability of failure, and a financial analysis. The longevity estimate and the probability of failure may apply to a component of an item of equipment or a particular item of equipment. The financial analysis may apply to one or more of the following: maintenance activity, a component, and an item of equipment.

Step S52 may be carried out in accordance with various alternate procedures. Under a first procedure, the determination of a predictive maintenance requirement comprises estimating longevity of a component based on a historical longevity of at least one of the component and an analogous component. The determining of a predictive maintenance requirement may be based upon estimating a remaining life span of a component by determining a usage time span between an installation date of the component and a subsequent date, and deducting the usage time span from the longevity for the corresponding component. Under a second procedure, the determination of the maintenance requirement comprises estimating a probability of failure of a component based on a historical probability of failure of at least one of the component and an analogous component. Under a third procedure, the determination of the maintenance requirement comprises estimating a financial impact of a component based on a historical impact of at least one of the component and an analogous component. Under a fourth procedure, the data processing system 12 or the predictive maintenance controller 20 evaluates tracked performance data on at least one of a particular component and the item of equipment with respect to a defined performance standard. Based on the evaluation, the data processing system 12 or the predictive maintenance controller 26 predicts at least one required maintenance activity.

In step S54, the data processing system 12 or the resource planner 14 plans for the availability of at least one of resources and a component for performing maintenance consistent with the configuration maintenance requirement and the predictive maintenance requirement.

In general, step S54 may comprise scheduling and bringing together at least two of the following resources at a specific time and place: a requisite component, technical instructions, supporting equipment, acceptance criteria and procedures, tools, and repair personnel. For example, step S54 includes obtaining the component for the target configuration and scheduling human resources consistent with availability of the component. Further, the data processing system may establish a universal representation of components to facilitate at least one of the acquisition of components from multiple sources, interchangeability of components, and tracking of component utilization. The scheduler 60, the resource planner 14 or both may participate in scheduling and bringing together of resources in a coordinated manner consistent with a maintenance plan.

In step S54, the planning of the resource planner 14, the scheduler 60 or both, may be accomplished in accordance with various alternative techniques or a combination of various alternate techniques. Under a first technique, the planning involves scheduling performance of the required maintenance activity at a defined respective time based upon a prediction of the predictive maintenance requirement. For example, the predictive maintenance controller 20 may determine a predictive maintenance requirement. The resource planner 14 may coordinate the predictive maintenance requirement with other maintenance activity for the item of equipment. Under a second technique, the planning involves scheduling performance of the required maintenance activity based on the configuration maintenance requirement. For example, the configuration monitor 22 may determine an upgrade requirement for upgrading the actual configuration to the target configuration if the actual configuration is noncompliant. The resource planner 14 may coordinate the upgrade requirement with other maintenance activity for the item of equipment. Under a third technique, the planning involves planning for the acquisition of at least one of the resources and the component consistent with the configuration maintenance requirement of step S50 and the predictive maintenance requirement of step S52. Under a fourth technique, the planning involves planning for the delivery of at least one of the resources and the component for a time interval at a common geographic location.

The planning of maintenance, repair and overhaul activities of step S54 of FIG. 6 may be executed in accordance with several alternative techniques that are not mutually exclusive. In accordance with a first technique, the planning of step S54 includes procuring a required part for the desired configuration and scheduling human resources consistent with availability of the required part. In accordance with a second technique, step S54 includes procuring the required assembly for the configuration and scheduling human resources consistent with the availability of the required assembly. In accordance with a third technique, step S54 includes providing part level data on the mechanical equipment to a user via an input/output device (e.g., maintenance input/output device 10) for a given point in time within a usable life of the mechanical equipment. In accordance with a fourth technique, step S54 includes providing a serial number of a component of the mechanical equipment at any given point in time for a given point in time within its usable life to manage the at least one of the safety, reliability, and performance. In accordance with a fifth technique, step S54 may include scheduling and bringing together at least two of the following items at a specific time and place: requisite parts, technical instructions, supporting equipment, acceptance criteria and procedures, tools, and repair personnel.

FIG. 7 shows step S50 in greater detail than FIG. 6. For example, step S50 of FIG. 6 may comprise steps S20 through S26 of FIG. 7.

In step S20, a desired configuration of an item of equipment is established based on an engineering design or objective that meets a reliability, safety, or performance goal of the item of equipment. For example, the engineering design may be configured to meet a reliability goal based on statistical failure data on parts, assemblies, or the entire item of equipment. One or more data sources 10 may provide input information or desired configuration data for a particular item of equipment.

In one embodiment, the user of the engineering input/output device may Wish to update the previously desired configuration with a current desired configuration because of an engineering change. A user of the engineering input/output device (e.g., a computer work station) enters a desired configuration of the mechanical equipment into the configuration data storage allocation (e.g., desired configuration database) based on compliance with one or more of the following criteria: technical specifications, reliability, availability of equipment, safety regulations, regulatory requirements, and performance requirements. In one example, the user may enter an update of the desired configuration into the engineering input/output device to foster compliance with a new technical standard. In another example, the desired configuration may be updated on regular basis after an evaluation of reliability feedback on the item of equipment, an assembly thereof, or a part thereof. In yet another example, a user of the engineering input/output device may establish the desired configuration based upon operational performance of a part, an assembly, a component, or an entire mechanical equipment.

An update to the desired configuration may involve replacing an old part having a lesser longevity with a substituted part having a greater longevity. Likewise, an update to the desired configuration may involve replacing an old assembly having a lesser longevity with a substituted assembly having a greater longevity.

In step S22, an actual configuration of the item of equipment is evaluated based on an inspection or reference to an observed configuration data on a particular item of equipment or an up-to-date actual configuration data in the configuration data storage 30. In one embodiment, the configuration data storage allocation 30 comprises an actual configuration databases. The actual configuration database may be referred to as an as-maintained database because the database generally indicates the as-maintained or current condition of the item of equipment. An actual configuration database may be considered up-to-date if an inspection (of the particular item of equipment) was recently conducted within a maximum time interval from the present time. The actual configuration may be determined or verified based on disassembly and inspection of at least a portion of the particular item of equipment. A user of the maintenance input/output device (e.g., computer work station) enters an actual configuration of the item of equipment into the actual configuration database based on a physical inspection, a visual inspection, a test of the mechanical equipment, or reference to an up-to-date actual configuration database.

In step S24, the data processor 30 determines if the actual configuration complies with the desired configuration for the item of equipment. For example, the data processing system 12 or the configuration monitor 22 determines compliance based upon the logical and physical configuration of the item of equipment expressed as configuration data with respect a particular time. The data processing system 12 retrieves records of configuration data from the configuration data storage 30. For example, the data processing system 12 retrieves records of configuration data from the actual configuration database and the desired configuration database that are associated with the same item of equipment. The configuration data is generally time sensitive. The actual configuration and the desired configuration may be associated with time stamps to facilitate an evaluation of the latest condition of the item of equipment. The time stamps may indicate absolute time or a relative time relationship between the actual configuration and the desired configuration data.

The data processing system 12 may query or search the configuration data storage allocation (e.g., actual configuration database and the desired configuration database) by equipment identifier, assembly identifier, or part identifier to retrieve records for the same mechanical equipment. The records may be organized as files or another suitable data structure. Once one or more records for the item of equipment are retrieved, the data processing system 12 may compare data records on a record-by-record basis, where the compared records of configuration data are associated with substantially the same time period. The data processing system 12 identifies and flags differences in the physical and logical configuration of the mechanical equipment between actual configuration data and the desired configuration data associated with the same time period.

If the data processing system 12 determines that the actual configuration does not comply with the desired configuration, the method continues with step S26. However, if the data processor 30 determines that the actual configuration does comply with the desired configuration, the method ends with step S28.

In step S26, the data processing system 12 or the configuration monitor 22 plans upgrade requirements to upgrade the actual configuration to the desired configuration if the actual configuration is noncompliant. The data processing system 12 may determine the upgrade requirements by comparing the actual configuration to the desired configuration with regards to physical, logical, and time characteristics associated with the actual configuration and the desired configuration. For example, the data processing system 12 may identify a component (e.g., part or subassembly) of the item of equipment that is noncompliant (physically, logically or temporally) with the desired configuration. The identified noncompliant component may be stored in the planned maintenance data storage 32, the configuration data storage allocation on elsewhere along with an associated equipment identifier for the particular item equipment. Further, the upgrade requirements or configuration maintenance requirement may contain requisite labor requirements, modification instructions, supporting tool and equipment information, and acceptance criteria to install the identified noncompliant component and achieve the desired (i.e., upgraded) configuration.

The configuration monitor 22 may send the configuration maintenance requirement to the resource planner 14 or coordinator 55. The configuration maintenance requirement may include identified part number, a requirement date, and other informational elements required to achieve the upgrade configuration, or both to the materials management system 36. Following step S26, the method may continue with step S54 of FIG. 6.

In step S54 of FIG. 6, planner 14 or coordinator 55 may coordinate or reconcile one or more of the following: predictive maintenance requirements, configuration maintenance requirements, and general maintenance requirements. The configuration maintenance requirement may include scheduling data and planning data for bringing together resources, such as the requisite parts, tools, equipment for support of the effort, modification instructions for the human resources, acceptance criteria with testing equipment and repair personnel at a specific time and place to complete upgrade requirements to achieve the desired configuration.

FIG. 8 shows one illustrative set of procedures for carrying out step S52 of FIG. 6. The method of FIG. 8 begins in step S10.

In step S10, performance data is tracked on at least one particular component of the equipment. For example, the data processing system 12 may collect or gather performance data on a component of the equipment, an assembly of components, or the equipment as a whole. The data processing system 12 may gather or collect performance data from an operational data source 46 or a human resources data source 48. The operational data source 46 may represent a monitor or a sensor associated with the equipment for measuring a particular component, an assembly, or the performance of the equipment as a whole. In the method of FIG. 8, the particular component may be defined based on its relationship to other components the mounting position or geographic position of the particular component on the equipment and the context of the use of the particular component.

The human resources data source 48 may be associated with workers that enter data into a database or a user interface 26 on the performance of a component, an assembly, or on the equipment as a whole. The operational data on the equipment that is entered via a user interface (e.g., 26) or provided by the human resources data source 48 may be gathered by inspection of one or more of the following: sensors, monitors or other inspection of the equipment. The observed or collected performance data or operational data may be provided by the operational data source 46, the human resources data source 48, or both.

In step S12, the data processing system 12 predicts at least one required maintenance activity based upon the collected or observed performance data with respect to a defined performance standard. For example, the predictive maintenance controller 20 of the data processing system 12 predicts at least one required maintenance activity if the performance data indicates that a defined performance standard has not been met. The defined performance standard may be defined such that noncompliance indicates that predictive maintenance is required or that predictive maintenance is necessary at some future date or over some future time interval to achieve a certain reliability or availability of the equipment for productive use. In one embodiment, the performance standard is defined as a measurable achievement of a required specific task within limits established by design calculations or in-service observations. A defined performance standard may be based on one or more of the following: a compliance factor, a safety factor, a quality factor, an economic factor, and any other suitable factor. The predictive maintenance controller may store performance standard data and component data to compare to the collected or observed performance data from the data sources 10.

In step S14, the data processing system 12 schedules performance of the required maintenance activity based upon the predicting to define a predictive maintenance requirement. The predictive maintenance requirement may comprise one or more of the following: a predictive maintenance activity, a time frame or date for performing the predictive maintenance activity, one or more components, and resources. The scheduler 60 of the data processing system 12 may schedule performance of the required maintenance by considering the component data identifier, the maintenance identifier and any associated maintenance date as an input to the scheduler 60.

The resource availability module 55 may provide availability data to one or more of the following inputs to the scheduler 60: worker data, facility data, tool data, and component data. In one embodiment, the resource availability module 55 provides the availability of a component, a facility, a tool, a worker, an assembly and the equipment to perform maintenance at a perspective date and at a perspective location.

Following step S14, the scheduler 60 may facilitate communication of the predictive maintenance requirement to the resource planner 14 or the coordinator 56. The method may continue with step S54 of FIG. 6. The coordinator 56 may coordinate the following: predictive maintenance requirements, configuration maintenance requirements, and general maintenance requirements to form a resultant maintenance plan. The communication interface 24 may communicate the resultant maintenance plan to a management system 28 (e.g., resource allocation data processing system) via a communications network. In one example, management system 28 may contact a worker, a manager of a facility or another manager of a resource to coordinate the availability of resources necessary to meet or comply with the resultant maintenance plan.

FIG. 9 and FIG. 10 show illustrative examples of how a data processing system 12 may be used in conjunction with a communication network 102 to integrate various aspects of predictive maintenance in accordance with the invention.

In FIG. 9, a data processing system 12, the operational data source 46, the human resources data source 48, the resource allocation system 104, and the purchasing system 70, may be co-located at a common site or in close proximity to one another.

In contrast, the supplier data source 44 may communicate with the data processing system 12 over a communication network 102. The supplier data source 44 may be located at a supplier site. A supplier site refers to any site that is owned or controlled by the supplier of a component, an assembly, a system or the equipment. Similarly, a supplier data processing system 106 (e.g., an order fulfillment center) may be located at the supplier site. The purchasing system 70 communicates with the supplier data processing system 106 over communication network 54. The communication network 102 may comprise the Internet and intranet, a communication system that supports a switched circuit connection, a communication system that supports a virtual connection, a data packet network, or another suitable telecommunication interconnection.

The resource allocation system 104 may facilitate communications with workers for performing maintenance. The resource allocation system 104 may also facilitate the distribution of components supplied by the supplier internally within a maintenance provider (e.g., an MRO organization). For example, the resource allocation processing system 104 may support the logistics involved with distributing inventory of the maintenance organization internally to multiple (maintenance, repair or overhaul) facilities located in geographically disparate or widely separated regions. Accordingly, resource allocation system 104 may consider a transportation cost, freight cost, custom duties, scheduling of shipments, packaging of shipments, and other activities which are necessary to insure that timely and accurate provision of material, tools and the availability of workers.

The resource allocation system 104 assures that repairs may be carried out and maintenance may be carried out without disruption from the unavailability of a qualified worker, a suitable facility, a requisite tool, a requisite component, a requisite consumable or any other information within the time frame of scheduled by the scheduler 60 for performance of the predictive maintenance.

In FIG. 10, the data processing system 12 is coupled to at least one of a resource allocation data processing system 104 and a supplier data processing system 106 via a communications network 102. Like reference numbers in FIG. 9 and FIG. 10 indicate like elements. The communications network 102 may refer to the Internet, an intranet, a data packet network, a public switched telephone network, a circuit-switched telecommunications network, or some other telecommunications network.

The supplier data source 44, the operational data source 46 and the human resources data source 48 communicate with the data processing system 12 over one or more communication network 102. The data processing system 12, the purchasing system 70 and the personnel management system may be co-located. The purchasing system 70 preferably communicates with the supplier's data processing system 106.

The data processing system 12 supports electronic communication with the supplier data source 44. The electronic communication may facilitate reduced costs in maintaining one or more items of equipment through the availability of useful information on at least one of maintenance, repair, or overhaul (e.g., MRO) of equipment. For example, useful information may include performance data or manufacturing data. Performance data or manufacturing data may be made available to the data processing system 12 to foster determination of an accurate preliminary schedule or resultant schedule for predictive maintenance on the equipment.

The purchasing system supports communication with the supplier data processing system 106, such as a supplier order fulfillment center. Communication between the purchasing system 70 and the supplier data processing system 106 may be automated to facilitate the acquisition of component, an assembly of components, of system of components, or other materials to meet planned maintenance activity or maintenance requirements.

The operator or user of the equipment may reduce the downtime for the equipment by predicting potential failures of the equipment or breakdowns of the equipment in advance of such breakdowns or failures actually occurring. Maintenance activities are preferably performed in a proactive manner, as opposed to, a reactive manner after a defect or deficiency in the equipment has been identified through an inspection. The communication network 102 of FIG. 10 supports a distributed entity or maintenance provider that manages predictive maintenance of the equipment. A distributed entity or maintenance provider may have human resources (e.g., maintenance workers) and components of equipment that may be located at different geographic locations. Further, the equipment may be mobile or portable with geographic locations that change over time during normal use of the equipment (e.g., where the equipment represents a passenger airplane). The data processing system 12 (e.g., the resource planner 14) may use the preliminary schedule and the resource availability data provided as worker data, facility data, tool data, and component data to generate a resultant schedule or planned maintenance plan for performing predictive maintenance on the equipment. The resultant maintenance plan may comprise a scheme that includes one or more of the following elements: a predictive maintenance requirement, a configuration maintenance requirement, and a general maintenance requirement. The communication interface 24 provides an interface for allowing the data processing system 12 to communicate the resultant maintenance plan over a communication network 102 to a supplier data processing system 106, a resource allocation data processing system 104, or the like.

The supplier data processing system 106 may comprise an enterprise resource planning system or supplier fulfillment center, for example. The supplier data processing system 106 may support the maintenance entity's ordering of components, materials (e.g., consumable materials), tools (e.g., test equipment or diagnostic equipment) and other resources necessary to complete predictive maintenance of the equipment.

Referring to FIG. 10, the resource allocation system 104 may communicate with a wireless or landline communications infrastructure 108 via a communication network 102. The wireless or landline communication infrastructure 108 may be associated with the first worker terminal 110 through an nth worker terminal 112. The worker terminals (110, 112) represent electronic terminals of the workers who are responsible for maintaining the equipment. For example, each worker terminal (110, 112) may represent a mobile phone, a mobile terminal with a display, a pager, a personnel digital assistant, or another communications device.

In one embodiment, the worker terminals (110, 112) and the wireless communications infrastructure (108) supports a two-way messaging interface. Accordingly, the workers can interact with the resource allocation system to provide real time availability information and to check on future assignments of planned maintenance.

The foregoing description of the method and system describes several illustrative examples of the invention. Modifications, alternative arrangements, and variations of these illustrative examples are possible and may fall within the scope of the invention. Accordingly, the following claims should be accorded the reasonably broadest interpretation, which is consistent with the specification disclosed herein and not unduly limited by aspects of the preferred embodiments disclosed herein. 

1. A performance-based logistics contracting system comprising: an input system for defining contractual requirements comprising product data; a maintenance system comprising: a communication interface operable to receive: component data from a supplier data source, said component data corresponding to said product data; operational data from an equipment sensor; and worker qualifications data from a human resources system; memory storing the component data, operational data, and the worker qualifications data; a configuration monitor operable to determine a configuration maintenance requirement when an equipment configuration is out-of-date; a predictive maintenance controller coupled to the memory and comprising: a timer; a scheduler receiving time data, duration data, or both from the timer; and a maintenance module coupled to the scheduler and comprising a financial analyzer and a longevity estimator, a probability of failure predictor, or both; where the predictive maintenance controller is operable to determine a predictive maintenance plan based on the component data, worker qualifications data, the operational data, and a predictive maintenance factor; a resource planner operable to plan for availability of a component for performing maintenance consistent with the configuration maintenance requirement and operable to coordinate the configuration maintenance requirement and the predictive maintenance plan into a combined maintenance schedule for both the configuration maintenance requirement and the predictive maintenance plan; and where the communication interface is further operable to transmit the combined maintenance schedule: to a project personnel management system; and to a purchasing and inventory control system.
 2. The performance-based logistics contracting system of claim 1, where the predictive maintenance controller comprises at least the longevity estimator, and where the predictive maintenance factor is a longevity estimate.
 3. The performance-based logistics contracting system of claim 1, where the predictive maintenance controller comprises at least the probability of failure predictor, and where the predictive maintenance factor is a probability of failure estimate.
 4. The performance-based logistics contracting system of claim 1, where the resource planner is further operable to plan for the availability of the component at a geographic location.
 5. The performance-based logistics contracting system of claim 1, further comprising an allocation intermediary coupled to the communication interface and the scheduler.
 6. The performance-based logistics contracting system of claim 1, where the memory comprises: a first database comprising the component data and operational data; a second database comprising the worker qualifications data; and a third database comprising planned maintenance data.
 7. The performance-based logistics contracting system of claim 1, where the financial analyzer is operable to provide a cost estimate for the combined maintenance schedule.
 8. The performance-based logistics contracting system of claim 7, where the memory comprises a first database comprising repair data and parts list data.
 9. The performance-based logistics contracting system of claim 7, where the memory comprises a first database comprising geography definition data and planned work geography definition data.
 10. The performance-based logistics contracting system of claim 6, further comprising a fourth database comprising maintenance history data.
 11. The performance-based logistics contracting system of claim 1, further comprising an equipment maintenance worker terminal coupled to the project personnel management system through a communication network.
 12. The performance-based logistics contracting system of claim 1, further comprising a supplier order fulfillment center coupled to the purchasing and inventory control system through a communication network.
 13. A performance-based logistics contracting method comprising: defining contractual requirements comprising product data; receiving component data corresponding to said product data from a supplier data source, operational data from an equipment sensor, and worker qualifications data from a human resources system over a communication interface; storing the component data, the operational data, and the worker qualifications data in a memory; determining a configuration maintenance requirement when an equipment configuration is out-of-date; using a financial analyzer and a longevity estimator, a probability of failure predictor, or both in conjunction with a timer and a scheduler to determine a predictive maintenance plan based on the component data, the worker qualifications data, the operational data, and a predictive maintenance factor; planning for availability of a component for performing maintenance consistent with the configuration maintenance requirement; coordinating the configuration maintenance requirement and the predictive maintenance plan into a combined maintenance schedule for both the configuration maintenance requirement and the predictive maintenance plan; and transmitting the combined maintenance schedule through the communication interface to a project personnel management system and to a purchasing and inventory control system.
 14. The method of claim 13, where using comprises: using at least the longevity estimator, and where the predictive maintenance factor is a longevity estimate.
 15. The method of claim 13, where using comprises: using at least the probability of failure predictor, and where the predictive maintenance factor is a probability of failure estimate.
 16. The method of claim 13, where planning comprises: planning for the availability of the component at a geographic location.
 17. The method of claim 13, where storing comprises: storing the component data and operational data in a first database, storing the worker qualifications data in a second database; and further comprising storing planned maintenance data in a third database.
 18. The method of claim 17, further comprising storing maintenance history data in a fourth database, the maintenance history comprising historical configuration data and historical planned maintenance data.
 19. The method of claim 13, further comprising storing repair data and parts list data in a first database, and storing historical resource data in a second database.
 20. The method of claim 19, further comprising searching the memory for worker qualifications and availability.
 21. The method of claim 13, further comprising allocating maintenance personnel to perform the combined maintenance schedule based on simultaneous availability of the component and the maintenance personnel.
 22. The method of claim 13, where transmitting comprises: transmitting through the project personnel management system to an equipment maintenance worker terminal.
 23. The method of claim 13, where transmitting comprises: transmitting through the purchasing and inventory control system to a supplier order fulfillment center.
 24. A performance-based logistics contracting system comprising: an input system for defining contractual requirements comprising product data; means for receiving component data corresponding to said product data from a supplier data source, operational data from an equipment sensor, and worker qualifications data from a human resources system over a communication interface; means for determining a configuration maintenance requirement when an equipment configuration is out-of-date; means for determining a predictive maintenance plan based on the component data, the worker qualifications data, the operational data, and a predictive maintenance factor using a financial analyzer and a longevity estimator, a probability of failure predictor, or both in conjunction with a timer and a scheduler; means for planning for availability of a component for performing maintenance consistent with the configuration maintenance requirement; means for coordinating the configuration maintenance requirement and the predictive maintenance plan into a combined maintenance schedule for both the configuration maintenance requirement and the predictive maintenance plan; and means for transmitting the combined maintenance schedule through the communication interface to a project personnel management system and to a purchasing and inventory control system.
 25. The performance-based logistics contracting system of claim 25, where the means for determining uses at least the longevity estimator, and where the predictive maintenance factor is a longevity estimate for an equipment component.
 26. The performance-based logistics contracting system of claim 25, where the means for determining uses at least the probability of failure predictor, and where the predictive maintenance factor is a probability of failure estimate.
 27. The performance-based logistics contracting system of claim 25, where the means for transmitting further transmits the combined maintenance schedule to an equipment maintenance worker terminal.
 28. The performance-based logistics contracting system of claim 25, where the means for transmitting further transmits the combined maintenance schedule to a supplier order fulfillment center.
 29. The performance-based logistics contracting system of claim 25, further comprising: means for storing the component data and operational data; and means for storing the worker qualifications data. 